Update Homebrew formula to CodeTruss CLI v0.2.36 - #4
Merged
Conversation
The tap served 0.2.30 while the website and the newest attested release served 0.2.36. url and sha256 come from the immutable v0.2.36 GitHub release, not the website copy. Verified they are the same bytes: the downloaded release asset, the archive on codetruss.com, and a local rebuild from the tagged source all hash to 953e3f48725a7471043b48a55aedd33ef78854615a341dd95881d90eeae3e814, and `gh attestation verify` binds that digest to release.yml at refs/tags/v0.2.36 on a GitHub-hosted runner. The workflow's post-install assertion is version-pinned, so it moves with the formula. Leaving it at 0.2.30 would have failed the install test on both macOS legs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe Homebrew formula now installs Codetruss CLI 0.2.36. The test workflow validates the same version. ChangesCodetruss release update
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tap served 0.2.30 while the website and the newest attested release served 0.2.36.
Changes
Three lines, all version-coupled:
Formula/codetruss.rburl→ the v0.2.36 release assetFormula/codetruss.rbsha256→953e3f48725a7471043b48a55aedd33ef78854615a341dd95881d90eeae3e814.github/workflows/test.ymlcodetruss 0.2.36The workflow's assertion is version-pinned. Leaving it at 0.2.30 would have failed the install test on both macOS legs, so it moves with the formula.
Where the digest comes from
urlandsha256are taken from the immutable v0.2.36 GitHub release, not the website copy. They are the same bytes, verified rather than assumed — the downloaded release asset, the archive on codetruss.com, and a local rebuild from the tagged source all hash to953e3f48….Provenance, verified against the downloaded asset:
Falsification-checked so the pass means something: a single flipped byte, the wrong repository, the SBOM in place of the archive, and a mismatched
--source-refeach fail with a non-zero exit.Why 0.2.36 and not 0.2.35
0.2.35 was never tagged. Its Windows tests failed on a real path-separator defect that also silently disabled vendored-directory exclusion on Windows, so the release was held and fixed in 0.2.36 rather than shipped around.
Summary by CodeRabbit
New Features
Tests